Search results for "Technical debt"

showing 7 items of 7 documents

The entrepreneurial logic of startup software development : A study of 40 software startups

2021

Context: Software startups are an essential source of innovation and software-intensive products. The need to understand product development in startups and to provide relevant support are highlighted in software research. While state-of-the-art literature reveals how startups develop their software, the reasons why they adopt these activities are underexplored. Objective: This study investigates the tactics behind software engineering (SE) activities by analyzing key engineering events during startup journeys. We explore how entrepreneurial mindsets may be associated with SE knowledge areas and with each startup case. Method: Our theoretical foundation is based on causation and effectuatio…

FOS: Computer and information sciencesEffectuationKnowledge managementComputer scienceeffectuation theoryohjelmistotuotantopäätöksentekoSample (statistics)effectuation indexstartup-yrityksetComputer Science - Software Engineeringcase studySoftwareohjelmistoalasoftware startup engineeringMinimum viable productentrepreneurial logicsbusiness.industrySoftware developmentsoftware engineering for startupsSoftware Engineering (cs.SE)Technical debtNew product developmenttuotekehitysThematic analysisbusinessohjelmistokehitysSoftware
researchProduct

Omission of Quality Software Development Practices : A Systematic Literature Review

2018

Software deficiencies are minimized by utilizing recommended software development and quality assurance practices. However, these recommended practices (i.e., quality practices) become ineffective if software professionals purposefully ignore them. Conducting a systematic literature review (n = 4,838), we discovered that only a small number of previous studies, within software engineering and information systems literature, have investigated the omission of quality practices. These studies explain the omission of quality practices mainly as a result of organizational decisions and trade-offs made under resource constraints or market pressure. However, our study indicates that different aspe…

General Computer ScienceComputer scienceProcess (engineering)korjausvelkamedia_common.quotation_subjectsoftware managementohjelmistotuotantoammattietiikka02 engineering and technologyTheoretical Computer Science020204 information systemsPhenomenon0202 electrical engineering electronic engineering information engineeringInformation systemQuality (business)informational systems developmentmedia_commontietojärjestelmätbusiness.industrySoftware development020207 software engineeringlaatulaadunvarmistusystematic literature reviewsohjelmistosuunnitteluSystematic reviewRisk analysis (engineering)technical debtTechnical debtbehavioral software engineeringbusinessohjelmistokehitysQuality assurance
researchProduct

Investigating the causal mechanisms underlying the customization of software development methods

2017

Over the last four decades, software development has been one of the mainstream topics in the Software Engineering and Information Systems disciplines. Thousands of methods have been put forward offering prescriptions for software development processes. The goal of these methods is to produce high-quality software in a systematic manner. However, it is widely known that these methods are rarely followed as prescribed – developers often modify or skip different steps, practices, or quality rules recommended by software development methods. While a group of previous studies suggests that maximizing the flexibility and leanness of software development processes is the key driver of such custom…

Prosessiteoriatekninen velkaKirjallisuuskatsauksetohjelmistokehittäjätohjelmistotuotantosystematic literature reviewlaatubalancinginformation systems developmentGrounded theorytyötavatmenetelmättyömenetelmättechnical debtprocess theoryräätälöintisoftware development methodsbehavioral software engineeringohjelmistokehitysvaatimukset
researchProduct

ScrumBut as an Indicator of Process Debt

2022

Technical debt analysis is used to detect problems in a codebase. Most technical debt indicators rely on measuring the quality of the code, as developers tend to induce recurring technical debt that emerges along with evolution cycles. This debt can emerge when project pressure leads to process deviations, for instance. In agile methods like Scrum, such deviations are commonly known as ScrumButs (like Scrum but …), which can be considered as a form of process debt. In this paper, we investigate two recurring signs of process debt (i.e. code smells and anti-patterns) caused by Scrumbuts. Our contribution investigates typical ScrumBut practices found in agile projects in one company and we re…

anti-patterns.ketterät menetelmätprosessittechnical debtohjelmistotuotantoScrumButcode smellsprocess debtohjelmistokehitysongelmat113 Computer and information sciences2022 48th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)
researchProduct

Achieving agility and quality in product development -an empirical study of hardware startups

2020

Context: Startups aim at scaling their business, often by developing innovative products with limited human and financial resources. The development of software products in the startup context is known as opportunistic, agility-driven, and with high tolerance for technical debt. The special context of hardware startups calls for a better understanding of state-of-the-practice of hardware startups’ activities. Objective: This study aimed to identify whether and how startups can achieve product quality while maintaining focus on agility. Method: We conducted an exploratory study with 13 hardware startups, collecting data through semi-structured interviews and analysis of documentation. We pro…

business.industryComputer sciencemedia_common.quotation_subjectExploratory researchContext (language use)Peer reviewSoftwareEmpirical researchDocumentationHardware and ArchitectureTechnical debtNew product developmentQuality (business)Product (category theory)businessVDP::Teknologi: 500::Informasjons- og kommunikasjonsteknologi: 550SoftwareComputer hardwareInformation Systemsmedia_common
researchProduct

Seeking Technical Debt in Critical Software Development Projects : An Exploratory Field Study

2016

In recent years, the metaphor of technical debt has received considerable attention, especially from the agile community. Still, despite the fact that agile practices are increasingly used in critical domains, to the best of our knowledge, there are no studies investigating the occurrence of technical debt in critical software development projects. The results of an exploratory field study conducted across several projects reveal that a variety of business and environmental factors cause the occurrence of technical debt in critical domains. Using Grounded Theory method, these factors are categorized as ambiguity of requirement, diversity of projects, inadequate knowledge management, and res…

ta113Agile usability engineeringKnowledge managementbusiness.industryEmpirical process (process control model)Agile Unified Process020207 software engineering02 engineering and technologySoftware peer reviewcomputer.software_genreExtreme programming practicestechnical debtTechnical debt020204 information systemssoftware development0202 electrical engineering electronic engineering information engineeringLean software developmentbusinessohjelmistokehityscomputerAgile software development
researchProduct

Looking for Peace of Mind? Manage your (Technical) Debt : An Exploratory Field Study

2017

Background: In the last two decades Technical Debt (TD) has received a considerable amount of attention from software engineering research and practice. Recently, a small group of studies suggests that, in addition to its technical and economic consequences, TD can affect developers’ psychological states and morale. However, until now there has been a lack of empirical research clarifying such influences. Aims: In this study, we aim at taking the first step in filling this gap by investigating the potential impacts of TD and its management on developers’ morale. Method: Drawing from previous literature on morale, we decided to explore the influence of TD and its management on three dimensio…

ta222media_common.quotation_subjectApplied psychology02 engineering and technologyInterpersonal communicationthematic analysisAffect (psychology)Field (computer science)Empirical researchPolitical science0502 economics and business0202 electrical engineering electronic engineering information engineeringProductivityta512media_commonmixed-methodta113Management scienceQualitative interviews05 social sciences020207 software engineeringexploratory field studyinformation systems developmentFeelingtechnical debtTechnical debtsoftware developmentmoralebehavioral software engineeringohjelmistokehitys050203 business & management
researchProduct